Collapse All Expand All

Instance Manager provides the ability to install and manage multiple instances of a Temenos Infinity environment at an institution.

Installing Instance Manager

Download the Installer

To obtain the installer for Instance Manager, please contact a Temenos representative.

Launching the Installer

Upon selecting Run as Administrator, the file extraction begins. A pop-up window displays the status.

Once the extraction completes, the Instance Manager window opens.

Navigate through the following steps to complete the installation of Instance Manager

Accept Terms and Conditions

Read the Temenos Infinity License Agreement.

 If the terms are acceptable, click I Agree.

Click Next to proceed to the next installation step.

Choose Components

Six features are available for installation. Each feature, except for the DMZ services, must be installed. These features can be installed on one server, or across multiple servers, depending on the financial institution's configuration. Determine the features to be installed by selecting the check box next to the desired component(s).

The following table provides a description of each feature:

Feature	Description
Application Services	This feature is required and includes critical service applications that support the website and the API. This feature is typically installed on the same server as the Website feature.
Database	This feature is required and installs the Temenos SQL Server database on the SQL server. This feature should be installed on the application server as it creates the database remotely on the SQL server. The Database feature should not be installed directly on the SQL server. Multiple servers cannot be used to run this feature.
DMZ Services	This feature is optional and provides services used by externally facing connectors for the Collection solution and the Loan Origination solution such as WebLoan, CUDL, Dealertrack, and RouteOne. DMZ Services must be installed on a secured, publicly accessible web server (DMZ server) and should not be installed on the same server as the website, application, or database.
Processes	This feature is required and includes Windows services and batch executable programs which are critical for daily processing. This feature is typically installed on the same server as the Web and Application Services features. To install the Processes component, Microsoft SQL Server (2008 or greater) Command Line Utilities are required. An error message is received if the requirements are not installed. For more information on installing Microsoft SQL Server Command Line Utilities, please reference the Hardware and Software Requirements document. Multiple servers cannot be used to run this feature.
Reporting Services	This feature is required and installs all of Temenos Infinity's pre-defined reports as well as the services that support capabilities to create, edit, and execute reports. This feature is typically installed on the same server as the Web and Application Services features and, when configured, attach to the SQL Server for linking data to the reports. Multiple servers cannot be used to run this feature.
Website	This feature is required and installs the Temenos Infinity website that end users access through their browsers. Multiple servers can be used to run this feature in a load balanced setup (see Load Balancing section in this document).

Once all components have been identified, click Next.

Choose Install Location

A default installation location is selected by the installer, but this location can be changed by manually entering the location of the destination folder within the text box, or clicking Browse to locate the folder.

Once the destination folder is identified, click Install to initiate the installation process.

Completing the Installation

Upon clicking Install, a Status bar appears to display the progress of the installation. When finished, the status bar updates to Completed, and a message appears to identify that the setup was successful.

 Click Close to exit the Instance Manager Setup window.

Using Instance Manager

Once the installation process is complete, Instance Manager is available on the server to create and manage the Temenos instances at an institution.

The following tabs are available within Instance Manager to provide an overview of the installed instances at an institution, display the status of upgrades as they run, and create, upgrade, and/or delete instances as necessary:

• Installed Instances
• Create Instance
• Upgrade Instance
• Delete Instance
• View Logs

Installed Instances

The Installed Instances tab displays an overview of the installed instances at an institution, and provides the ability to easily access Server Manager for a particular instance.  

The grid in this tab displays the following columns of information for each instance:

Column	Description
Instance Name	Displays the name of the instance. Instances are listed alphabetically within the grid.
Database Server	Displays the database server of the instance’s database.
Database Name	Displays the name of the instance database.
Version	Displays the current installed version of the instance.
	Provides the ability to open Server Manager for that instance. Upon clicking this button, Server Manager opens in a new window. For more information on Server Manager, please see the Server Manager technical guide.

Create Instance

The Create Instance tab provides the ability to enter the information required to create a new instance of Temenos Infinity.

This tab includes the following sections of information to complete for each instance:

Field	Description
Application Identity
This section provides the ability to identify the Windows account information for the instance.
Domain	Enter the domain for the instance's Windows account.
Username	Enter the username to connect to the instance's Windows account.
Password	Enter the password to connect to the instance's Windows account.
Database
This section provides the ability to configure the database server name, database name, and database connection information for the instance.
Server	Enter the server name for the database.
Database	Enter the name of the database.
Database Connection	Select Windows Authentication or SQL Server Authentication to identify how the instance connects to the database. Select Windows Authentication to use the credentials of the current logged-in user. Select SQL Server Authentication to provide the username and password. When SQL Server Authentication is selected, the Login Name and Password are enabled to enter the values required to access the instance.
Share Folder
This section provides the ability to identify the share path location for the instance.
Share Folder	Enter the folder path location for the share path associated with the instance. This text box pre-populates with C://Share.
Reporting Services
This section provides the ability to configure the instance's Reporting Services service.
Server	Enter the server on which the Reporting Services service is installed.
Name	Enter the name of the virtual directory for the Reporting Services Web Service.
Name	Enter the name of the Temenos reports folder.
Use SSL?	Select the check box if the Report Server is configured for SSL.
Website
This section provides the ability to configure settings for the Temenos Infinity web application.
Choose Website	Select the parent website for the Temenos Infinity web application.  If the drop-down list is blank, the websites must be configured in IIS. Exit the installer, configure a website and then run the installer again.
Virtual Directory	Enter the name of the web application to be created for Temenos Infinity.
Virtual Path	Enter the full virtual path for the web application, including the virtual root.
Temenos Instance
Name	Enter a unique name for the Temenos instance. This name must be unique, or an error is displayed when trying to create the instance.

Creating an Instance

To create an instance:

• Complete the fields in each section of the Create Instance tab.
• Once all fields for the instance are complete, click Create Instance.
• If the name is unique, and all fields are complete, the instance is created, and added to the Installed Instances tab.

  If the name of the instance already exists, an error is displayed to identify that the instance name already exists, and a new name must be entered. Similarly, if all required fields are not configured for the instance, an error is received upon clicking Create Instance.

Upgrade Instance

The Upgrade Instance tab provides institutions with the ability to upgrade their installed instances.

The grid in this tab displays the following columns of information for each instance:

Column	Description
Instance Name	Displays the name of the instance. Instances are listed alphabetically within the grid.
Database Server	Displays the database server of the instance’s database.
Database Name	Displays the name of the instance database.
Version	Displays the current installed version of the instance.
Last Upgrade Date	Displays the date the instance was created or the last date the instance was successfully upgraded.
Upgrade	Provides the ability to select the desired instances to upgrade. This check box is automatically selected when the version drop-down list in the top of the tab is set to Upgrade instances on previous versions, or Upgrade all instances.
Upgrade Status	Displays one of the following values to identify the status of the upgrade for an instance: Status Description Cancelled Identifies that the upgrade was cancelled. Completed Identifies that the instance was successfully created or upgraded to the current version of instance manager. Failed Identifies that the upgrade failed. In Progress Identifies that the upgrade is in progress. Pending Identifies that the instance was selected for an upgrade, but the upgrade process has not yet begun for the instance. Upgrade Needed Identifies that an upgrade is required as the instance is on a version older the version of instance manager.
	Provides the ability to open Server Manager for that instance. Upon clicking this button, Server Manager opens in a new window. When an instance’s Server Manager is launched from within Instance Manager, and changes are made to shared fields, the updated values for these fields are not reflected until Instance Manager is re-launched. More than one instance of server manager can be open simultaneously. Services must be restarted in Server Manager after upgrading multiple instances. Upon a successful upgrade, this button is highlighted green for each instance where Server Manager must be launched.

The drop-down list in the top of the tab allows users to filter the instances that appear within the grid according to their version, or automatically select certain instances for upgrade.

This drop-down includes the following options:

Version Selection	Description
Instances on previous versions	Displays the instances that are not on the current version of instance manager. This is the default value for the drop-down list.
Instances on the current version	Displays the instances that are on the current version of instance manager.
All instances	Displays all instances on all versions of instance manager.
Upgrade instances on previous versions	Automatically selects the ‘Upgrade’ box for all instances on old versions of instance manager.
Upgrade all instances	Automatically selects the ‘Upgrade’ box for all instances.

This tab also includes the following buttons to start or cancel the upgrade process:

Button	Description
Upgrade Selected Instance(s)	Initiates the upgrade process for the selected instance(s). Clicking this button immediately stops all services for an instance, prior to upgrading the instance.
Cancel Upgrade(s)	Cancels the upgrade process for the selected instance(s). This button is only enabled when there are two or more upgrades are in progress.

Upgrading One or More Instances

The Upgrade Selected Instance(s) button initiates the upgrade process for the instances selected within the Upgrade Instance tab.

To upgrade one or more an instances:

• Select the check box in the Upgrade column for the desired instance(s), or select one of the following options from the Version filter in the top of the tab:
  • Upgrade instances on previous versions
  • Upgrade all instances
• Click Upgrade Selected Instances.
• The behavior that occurs upon selecting this button is dependent on the number of instances selected to upgrade.
  • If no instances are selected in the Upgrade column, an error message is displayed to identify that one or more instances must be selected to upgrade.
  • If a single instance is selected in the Upgrade column, a message appears to identify that the instance will be unavailable during the upgrade, and confirm that the user wants to continue. Upon selecting Yes, the upgrade begins for the selected instance, and the Upgrade Status column is updated with the result. Upon completion of the upgrade, Server Manager automatically opens for the instance.
  • If multiple instances are selected in the Upgrade column, or an Upgrade instance option is selected within the Version drop-down, a message appears to identify the number of instances to be upgraded, or confirm that all instances are being upgraded. This message also identifies that the instances will be unavailable during the upgrade, and asks for confirmation that the user wants to continue. Upon selecting Yes, the upgrade begins for the first instance. Upon completion, the Upgrade Status column is updated with the result, and the upgrade proceeds to the next instance.
• When upgrading two or more instances:
  • Once the instances are successfully upgraded, a Server Manager prompt appears to identify that services must be restarted on the Common tab of Server Manager for all upgraded Instances. The Server Manager button is highlighted green in the Upgrade Instance tab for each instance where it must be launched.
  • If an upgrade fails for an instance, a message appears after the first failure to identify that a failure occurred, and that more details can be found in the Upgrade Log. This message also asks the user to confirm if the remaining upgrades should continue. 
    • If Yes is clicked, the remaining upgrades continue without interruption. In the event of additional failures, the upgrade process continues to the next upgrade.
    • If No is clicked, the process does not continue upgrading the additional instances.

Canceling an Upgrade

The Cancel Upgrade(s) button provides the ability to cancel the upgrade process for the selected instance(s). By default, this button is disabled until two or more instances are selected to upgrade.

To cancel the upgrade process:

• Click Cancel Upgrade(s).
• Upon clicking this button, a message appears to confirm that any upgrades that have not completed, or are not in progress, should be cancelled.
• Click Yes to cancel any upgrades that have not started, or No to continue with the upgrade process.

  If more than one instance in being upgraded, all completed upgrades are unaffected when the upgrade process is cancelled, and any upgrades that have not started are not attempted.

Delete Instance

The Delete Instance tab provides institutions with the ability to remove installed instances from Instance Manager.

The grid in this tab displays the following columns of information for each instance:

Column	Description
Instance Name	Displays the name of the instance. Instances are listed alphabetically within the grid.
Database Server	Displays the database server of the instance’s database.
Database Name	Displays the name of the instance database.

Deleting an Instance

The Delete Selected Instance button provides the ability to remove an instance from Instance Manager.

To delete an instance:

• Highlight the desired instance within the grid, and click Delete Selected Instance.
• A message appears to identify that all related files for the instance will be deleted, and confirm that the instance should be removed.
• Upon clicking Yes, a second message appears to identify that the action is permanent and cannot be reversed. The message also asks the user to again confirm that the instance should be removed.
• Upon clicking Yes, a third message appears to confirm that the instance is being deleted, and identify that the instance database will not be removed. Click Yes to proceed with removing the instance, or no to retain the instance in Instance Manager.
• When an instance is removed from Instance Manager, the following items associated with the instance are also deleted:
  • All IIS Application pools and services
  • The instance sharepath folder, sub folders, and files 
  • All references to the instance in Instance Manager

    All LMS and Reporting Services databases for the instance are NOT removed.

• When an instance is fully deleted, a message appears to confirm that the instance has been successfully uninstalled. Click OK to close the message.
• If an error occurs that prevents an instance from fully deleting, a message appears to identify that the instance has been uninstalled, but one or more errors occurred. Please review the error log for details.

View Logs

The View Logs tab provides institutions with the ability to review the status of new installs and upgrades as they run, as well as errors that occur.

This tab is a read-only text box that displays the progress of new installs and upgrades launched in Instance Manager, as well as details for any errors that occur during the installation or upgrade.

 

 

---

©2023 Temenos Headquarters SA - all rights reserved.

Send Feedback